I was following the post below to migrate PF from exchange 2007 to exchange 2013

http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-4-step-by-step-exchange-2007-to-2013-migration.aspx

Migration request never got to AutoSuspended state, instead it's showing StalledDueToC which I found a fix for under the following link

http://www.msexchange.org/kbase/ExchangeServerTips/ExchangeServer2013/TransitioningMigration/exchange-2013-stalledduetoci-error.html

When I checked Microsoft Exchange Security Groups OU "ContentSubmitters" group did not exist, however all other groups had a space in their names. I went ahead a created a group without the space, as shown in the article and restarted both services (Microsoft Exchange Search and the Microsoft Exchange Search Host Controller)

when I check Get-PublicFolderMigrationRequest | Get-PublicFolderMigrationRequestStatistics, I am still seeing StalledDueToCI

Can someone confirm that ContentSubmitters does not need a space in the middle? I am on Exchange 2013 CU3

Hi

Yes the name is correct. did you do the following:

Change the security on the group and allow Administrators and NetworkService accounts Full Control;
Restart the Microsoft Exchange Search and the Microsoft Exchange Search Host Controller services on every Mailbox server.

Yes, I did change the security on the group and allowed Administrators and NetworkService accounts Full Control

either I didn't wait long enough or reboot of the exchange server resolved the issue

• Marked as answer by net_tech Saturday, January 04, 2014 6:26 PM

This fix seems to work only temporarily. I am migrating some larger mailboxes >7Gb and they are "CopyingMessges" for one or 2% further, and then they go "StalledDueToCI" again.

Restarting the service "Microsoft Exchange Mailbox Replication" seems to get the mailbox move started again, but only temporarily.

Does anyone please have a better fix? I will be sitting in front of this computer all night, otherwise.

Thanks.

• Edited by ken_at_novus 8 hours 9 minutes ago

The "contentSubmitters"fix seems to work only temporarily. When migrating some larger mailboxes (>7Gb) from Exchange 2010 to Exchange 2013 they stall with "StalledDueToCI" again.

Restarting the service "Microsoft Exchange Mailbox Replication" seems to get the mailbox move started again, but only temporarily.

What fixed it was "Set-MailboxDatabase "<Your database name>" -IndexEnabled:$False"

After that, all mailboxes migrated quickly.

I expect that "Set-MailboxDatabase "<Your database name>" -IndexEnabled:$True" is required after the migration finishes, but I haven't tested that yet.

Perhaps someone at Microsoft could check this to ensure that it does not cause any future problems, and maybe fix whatever is wrong with the mailbox migration system in the new Exchange 2013 GUI. Spending several days tracking down all the obscure errors in what should be a simple process is not good.

 

• Edited by ken_at_novus 15 hours 18 minutes ago
• Proposed as answer by ken_at_novus 13 hours 6 minutes ago